<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Using Bochs</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="Bochs User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="How to write your own keymap table"
HREF="keymap.html"><LINK
REL="NEXT"
TITLE="Search order for the configuration file"
HREF="search-order.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Bochs User Manual</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="keymap.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="search-order.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="USING-BOCHS"
></A
>Chapter 5. Using Bochs</H1
><P
>After starting Bochs either from the command prompt or the OS shell, the following
steps are done before the simulation is running.
<P
></P
><OL
TYPE="1"
><LI
><P
>parse <A
HREF="using-bochs.html#COMMANDLINE"
>command line</A
> (except bochsrc options)</P
></LI
><LI
><P
>load selected config file (<A
HREF="bochsrc.html"
>bochsrc</A
>) or <A
HREF="search-order.html"
>search</A
> for the default one</P
></LI
><LI
><P
>parse remaining command line options (<A
HREF="bochsrc.html"
>bochsrc</A
> syntax)</P
></LI
><LI
><P
>initialize configuration interface</P
></LI
><LI
><P
>enter <A
HREF="textconfig.html"
>start menu</A
> / dialog (unless quick start mode is enabled)</P
></LI
><LI
><P
>initialize all parts of the simulator</P
></LI
><LI
><P
>enter <A
HREF="internal-debugger.html"
>debugger</A
> prompt / dialog (if present)</P
></LI
><LI
><P
>enter the simulation loop</P
></LI
></OL
></P
><P
>During simulation, Bochs usually generates more or less log output. By default it
is sent to the console, otherwise to the specified <A
HREF="bochsrc.html#BOCHSOPT-LOG"
>log file</A
>.
The amount of output can be controlled with the <A
HREF="bochsrc.html#BOCHSOPT-DEBUG-INFO-ERROR-PANIC"
>log options</A
>
in bochsrc, the start menu and the runtime configuration.</P
><P
>Under certain conditions Bochs can cause a <A
HREF="common-problems.html#LOGEVENT-PANIC"
>panic</A
>
and usually asks the user what to do. If such a panic happens during startup, it is
mostly a configuration or permission problem and we recommend to quit Bochs and to
review the bochsrc options used.</P
><P
>To quit the simulation, the "power" button in the Bochs <A
HREF="textconfig.html#HEADERBAR"
>headerbar</A
>
should be used, unless the guest OS has the capability to turn off the computer (APM or ACPI).</P
><P
>If a Bochs runtime issue cannot be fixed by configuration changes and it has not yet
been reported in the <A
HREF="mailinglist.html#BOCHS-DEVELOPERS"
>bochs-developers mailing list</A
> or the SF trackers for Bochs, it should be reported in
the mailing list or the <A
HREF="feedback-support.html#SF-TRACKERS"
>SF bug tracker</A
> for the Bochs project.</P
><DIV
CLASS="SECTION"
><H1
CLASS="SECTION"
><A
NAME="COMMANDLINE"
>5.1. Command line arguments</A
></H1
><P
>The following table shows the arguments that can be used on the command line.
For other arguments, see section <A
HREF="bochsrc.html"
>bochsrc</A
>.
<DIV
CLASS="TABLE"
><A
NAME="AEN2878"
></A
><P
><B
>Table 5-1. command line arguments</B
></P
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><COL><COL><THEAD
><TR
><TH
>Argument</TH
><TH
>Description</TH
></TR
></THEAD
><TBODY
><TR
><TD
>-q</TD
><TD
>quick start (skip configuration interface)</TD
></TR
><TR
><TD
>-f <TT
CLASS="REPLACEABLE"
><I
>filename</I
></TT
></TD
><TD
>specify configuration file</TD
></TR
><TR
><TD
>-log <TT
CLASS="REPLACEABLE"
><I
>filename</I
></TT
></TD
><TD
>specify Bochs log file</TD
></TR
><TR
><TD
>-dbglog <TT
CLASS="REPLACEABLE"
><I
>filename</I
></TT
></TD
><TD
>specify Bochs internal debugger log file</TD
></TR
><TR
><TD
>-n</TD
><TD
>don't try to load a configuration file</TD
></TR
><TR
><TD
>-r <TT
CLASS="REPLACEABLE"
><I
>path</I
></TT
></TD
><TD
>specify path for restoring state</TD
></TR
><TR
><TD
>-noconsole</TD
><TD
>disable console window (Windows only)</TD
></TR
><TR
><TD
>--help</TD
><TD
>display help message and exit</TD
></TR
><TR
><TD
>--help features</TD
><TD
>display available features / devices and exit</TD
></TR
><TR
><TD
>--help cpu</TD
><TD
>display supported CPU models and exit (CPU level &#62; 4 only)</TD
></TR
></TBODY
></TABLE
></DIV
></P
><P
>These arguments are handled directly after starting Bochs. The next step is to load
a default or specified configuration file (unless disabled with -n). Then the rest
of the command line (<TT
CLASS="FILENAME"
>bochsrc</TT
> options) is parsed. This is done after reading the
configuration file so that the command line arguments can override the settings
from the file.</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="keymap.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="search-order.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>How to write your own keymap table</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Search order for the configuration file</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>